encountering problems correcting error message 2738

Category: Geeks r Us

Post 1 by bozmagic (The rottie's your best friend if you want him/her to be, lol.) on Thursday, 29-May-2008 2:34:09

Hi. Well, subject is as above. I'm encountering an error message 2738 VB script could not access the system when I try to install and run some software downloads, for example, Channel 4OD. I contacted the support team by means of their contact form and they sent me some steps to fix this error message using command prompt and copy and paste. I got as far as the first line they told me to copy and paste, but then JAWS wouldn't let me copy that line so I couldn't proceed any further, so how have other Vista users got on when they encountered it? Is there a screenreader friendly way of fixing this error?

Jen.

Post 2 by bozmagic (The rottie's your best friend if you want him/her to be, lol.) on Thursday, 29-May-2008 2:43:32

In fact, this is the reply I got from Channel 4OD Tech Support and also, as you'll see, it isn't very screenreader/VI friendly.


We have researched this error as it appears to be a common problem on
Windows Vista with all kinds of software.

To resolve the problem:

1. Click Start > Programs

2. Locate 'Command Prompt' in the accessories menu and right-click and press
'Run as Administrator'

3. Highlight all of the line below, right click on it and choose Copy.

CD

4. Right click in the black Command Prompt Window and choose Paste, then
click the Enter/Return button

5. Highlight all of the line below, right click on it and choose Copy.

CD windowssystem32

6. Right click in the black Command Prompt Window and choose Paste, then
click the Enter/Return button

7. Highlight all of the line below, right click on it and choose Copy.

regsvr32 jscript.dll

9. Right click in the black Command Prompt Window and choose Paste, then
click the Enter/Return button

A message box should now appear stating that this step was successful. Now
try again to install 4oD.

If the problem persists you try steps 10 and 11.

10. Highlight all of the line below, right click on it and choose Copy.

regsvr32 vbscript.dll

11. Right click in the black Command Prompt Window and choose Paste, then
click the Enter/Return button

A message box should now appear stating that this step was successful. Now
try again to install 4oD.

Jen.

Post 3 by Squiggles (Account disabled) on Thursday, 29-May-2008 7:21:52

If you knew how to use jaws you could copy and paste jut fine. Use the applications key. First off, trying to get aything to run in Vista can be quite a cumbersome task anyway so I'm not quite sure why you'd use it anyway, unless it came with a brand new machine, in which case I strongly sugest you buying a copy of xp or getting it from somewhere. In any event, giving an error code to a program that we have no idea what you are dealing with doesn't help us at all, so you really should be more specific. Besides, those commands are short enough anyway just type them. Always try to do every possible way first, before wining to the boards, please.

Post 4 by b3n (I'm going for the prolific poster awards!) on Thursday, 29-May-2008 17:26:43

@2, I kno exactly what she's talking about - unless your reffering to one of us actually trying to install 4od on a vista machine.
Could one of the vista people post to this (rat)?
I'm quite sure that she doesn't need to cd to the directories coz unless they changed something big, system32's still going to be in %path% so i would have just told her to run regsvr from run, but I don't kno how to invoke a run dialog as root or whatever you call it.

Post 5 by Squiggles (Account disabled) on Friday, 30-May-2008 7:19:32

As I have said, it is not worth your time to even both with running anything on the command line in vista, you most likely get errors. I think my point has been very well demonstrated.

Post 6 by rat (star trek rules!) on Friday, 30-May-2008 12:37:44

that's not exactly true, i run vista and do stuff with command line a lot.

Post 7 by bozmagic (The rottie's your best friend if you want him/her to be, lol.) on Saturday, 31-May-2008 10:54:08

Well never mind guys, I've fixed it now anyway along with a couple of other errors floating around, thanks to the MSDN forums.

Jen.